Meridian event procedures allow you to customize the way Meridian works by adding your own functionality onto what Meridian already does. When a user executes certain commands in one of the Meridian client applications, Meridian performs a sequence of actions. At various steps in the sequence, Meridian declares that an action (event) is occurring to which VBScript can react. Meridian checks for the definition of a specific VBScript procedure (event handler) that corresponds to each event. If the procedure exists, Meridian executes it before proceeding on to the next step in the sequence. All VBScript event procedures are stored in a code block in the vault separate from the code blocks for the configuration expressions.
Event procedures are more powerful than configuration expressions. Each configuration expression is a single statement to be evaluated. Event procedures can contain many statements and provide additional advantages. Event procedures can:
Note The order of the events may change slightly in new releases to accommodate new functionality or to resolve problems and cannot be guaranteed. Test all customization that relies on event procedures with each upgrade before deploying the customization for production use.
Each category of event procedures is described in the following topics:
Related concepts
Understanding the names of events
Understanding the order of events
Understanding the Meridian Enterprise Script Editor
Understanding the Microsoft Script Debugger
Understanding configuration expressions
Understanding the Meridian object model
Understanding the Meridian functions
Understanding automation objects
Understanding object arguments
Understanding VBScript and the Meridian Web Client
Understanding the CurrentPropertyName property
Related tasks
Creating and editing event procedures
Limiting events generated by VBScript
Understanding the effects of custom scripting
Related information